User equipment controlled mobility in an evolved radio access network

ABSTRACT

Briefly, in accordance with one or more embodiments, a user equipment (UE) may enter into an E-UTRAN Routing Area Paging Channel state, and is configured with an E-UTRAN Routing Area and an Anchor identifier to identify an anchor evolved Node B (eNB) for the UE. The UE selects to a new cell without performing a handover procedure, and performs a cell update procedure. The UE also may enter into a Cell Update Connected state, and is configured with an Anchor identifier. The UE selects to a new cell, performs a cell update procedure, performs a buffer request procedure, and performs a cell update procedure to download buffered data and to perform data transmission with the new cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional under 35 U.S.C. § 121 of and claimspriority under 35 U.S.C. § 120 to U.S. patent application Ser. No.15/542,262, filed Jul. 7, 2017, entitled USER EQUIPMENT CONTROLLEDMOBILITY IN AN EVOLVED RADIO ACCESS NETWORK which in turn claimspriority under 35 U.S.C. § 371 to International Application No.PCT/US2015/066000 filed Dec. 16, 2015, entitled USER EQUIPMENTCONTROLLED MOBILITY IN AN EVOLVED RADIO ACCESS NETWORK which in turnclaims the benefit of U.S. Provisional Application No. 62/145,370 filedApr. 9, 2015 (Docket No. P83804Z). Said application Ser. No. 15/542,262,PCT/US2015/066000 and 62/145,370 are hereby incorporated herein byreference in their entirety.

BACKGROUND

The Internet of Things (IoT) refers to a collection of sensors havingnetwork connectivity to allow the distributed collection and exchange ofdata. Massive deployment of a large number of IoT devices to connect toexisting wireless wide area networks (WWANs) operating in accordancewith a Third Generation Partnership Project (3GPP) may present newproblems that should be addressed. Evolved Packet Core (EPC) signalingmay experience overload due to frequent state changes between the twocurrent network states, the connected state (EMM_Connected) and and theidle state (EMM_Idle). Furthermore, many IoT devices are not connectedto power, and therefore should operate with very efficient batteryusage. In addition, IoT devices may transmit smaller bursts of data atmore frequent intervals, the delay for uplink transmissions should bevery low delays. Although some of these issues may be addressed undercurrent architectures, the issues are not all addressed simultaneously.

One approach may be to keep the IoT user equipment (UE) permanently in aconnected state such as in EMM_Connected or RRC_CONNECTED, in order toaddress the signaling load due to state transitions and provide lowuplink delays. This approach, however, would have a huge impact onbattery life because the UE continuously performs measurements tosupport the Handover procedure, and because radio interface signalinginvolves performing the handover at every cell change. Also, while theEPC signaling load due to state transitions is reduced, a different typeof EPC signaling load, due to frequent handovers, may be created.

The impact on battery life due to a permanent RRC_CONNECTED state may besomewhat mitigated by using longer values for Connected modediscontinuous reception (DRX) cycle (C-DRX cycle), but this approach islikely to degrade the handover performance. Namely, in cases where theUE is moving very fast, the likelihood of handover failure increasesbecause the serving cell signal becomes weaker as the target cell signalgets stronger, and hence the handover (HO) command sent by the servingcell may not successfully be received. The use of a longer C-DRX cyclewill only increase the handover failure rate because in the interest ofpower saving, the UE performs measurements only during the receivingoccasion of the C-DRX cycle and hence a longer C-DRX cycle results inless frequent measurements.

In the case of a handover failure, the UE will declare radio linkfailure (RLF) and more signaling will be involved. The case of radiolink failure (RLF) indicates that the UE performs an RRC connectionreestablishment, which involves at least three messages over the airinterface, and additionally there may be a delay to declare radio linkfailure during handover such as delay from expiry of the RLF timer.Moreover, subsequent to RLF, the UE has control over selecting the newcell, which means the network has no control over cell selection.

DESCRIPTION OF THE DRAWING FIGURES

Claimed subject matter is particularly pointed out and distinctlyclaimed in the concluding portion of the specification. However, suchsubject matter may be understood by reference to the following detaileddescription when read with the accompanying drawings in which:

FIG. 1 is a diagram of a network illustrating mobility handling in afirst access stratum state using X2 paging and cell update procedures inaccordance with one or more embodiments;

FIG. 2 is a diagram of a network further illustrating mobility handlingin the first access stratum state as shown in FIG. 1 in accordance withone or more embodiments;

FIG. 3 is a diagram of a network illustrating mobility handling in asecond access stratum state using buffer request and cell updateprocedures in accordance with one or more embodiments;

FIG. 4 is a diagram of a network illustrating mobility handling in thefirst access stratum state using a centralized architecture inaccordance with one or more embodiments;

FIG. 5 is a diagram of a network further illustrating mobility handlingin the first access stratum state as shown in FIG. 4 in accordance withone or more embodiments;

FIG. 6 is a diagram of a network illustrating mobility handling in thesecond access stratum state using a centralized architecture inaccordance with one or more embodiments;

FIG. 7 is a diagram of a network further illustrating mobility handlingin the second access stratum state as shown in FIG. 6 in accordance withone or more embodiments;

FIG. 8 is a block diagram of an information handling system capable ofproviding location information for Voice over WLAN emergency calling inaccordance with one or more embodiments;

FIG. 9 is an isometric view of an information handling system of FIG. 6that optionally may include a touch screen in accordance with one ormore embodiments; and

FIG. 10 is a diagram of example components of a wireless device inaccordance with one or more embodiments.

It will be appreciated that for simplicity and/or clarity ofillustration, elements illustrated in the figures have not necessarilybeen drawn to scale. For example, the dimensions of some of the elementsmay be exaggerated relative to other elements for clarity. Further, ifconsidered appropriate, reference numerals have been repeated among thefigures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components and/or circuitshave not been described in detail.

In the following description and/or claims, the terms coupled and/orconnected, along with their derivatives, may be used. In particularembodiments, connected may be used to indicate that two or more elementsare in direct physical and/or electrical contact with each other.Coupled may mean that two or more elements are in direct physical and/orelectrical contact. However, coupled may also mean that two or moreelements may not be in direct contact with each other, but yet may stillcooperate and/or interact with each other. For example, “coupled” maymean that two or more elements do not contact each other but areindirectly joined together via another element or intermediate elements.Finally, the terms “on,” “overlying,” and “over” may be used in thefollowing description and claims. “On,” “overlying,” and “over” may beused to indicate that two or more elements are in direct physicalcontact with each other. However, “over” may also mean that two or moreelements are not in direct contact with each other. For example, “over”may mean that one element is above another element but not contact eachother and may have another element or elements in between the twoelements. Furthermore, the term “and/or” may mean “and”, it may mean“or”, it may mean “exclusive-or”, it may mean “one”, it may mean “some,but not all”, it may mean “neither”, and/or it may mean “both”, althoughthe scope of claimed subject matter is not limited in this respect. Inthe following description and/or claims, the terms “comprise” and“include,” along with their derivatives, may be used and are intended assynonyms for each other.

Referring now to FIG. 1 and FIG. 2, diagrams of a network illustratingmobility handling in a first access stratum state using X2 paging andcell update procedures in accordance with one or more embodiments willbe discussed. It should be noted that the embodiments and examplesdiscussed herein may be directed to a network and devices operating inaccordance with a Third Generation Partnership Project (3GPP).Furthermore, the embodiments and examples discussed herein also mayapply to a new radio access technology that has radio access networkarchitecture similar to an Evolved Universal Mobile TelecommunicationsSystem Terrestrial Radio Access Network (E-UTRAN) in accordance with a3GPP standard and beyond such as a Fifth Generation (5G) network andbeyond, and the scope of the claimed subject matter is not limited inthese respects. As discussed herein, two new access stratum states aredescribed to implement a user equipment (UE) controlled mobilityprocedure referred to as Cell Update mobility. The first access stratumstate may be referred to as evolved universal mobile telecommunicationssystem (UMTS) terrestrial radio access (E-UTRAN) Routing Area PagingCannel (ERA_PCH), and the second access stratum state may be referred toas Cell Update Connected (CU_CNCTD). In one or more embodiments, theERA_PCH state and the Cell Update procedure bear some similarities withthe UTRAN URA_PCH state and Cell/URA Update procedures as described in3GPP Technical Standard (TS) 25.331 with some differences. Thesimilarities primarily may include the following. When in ERA_PCH state,the UE is in EMM_Connected state. When in the ERA_PCH state, the UE isin PMM Connected state. ERA is a collection of E-UTRAN cells, and URA iscollection of UTRAN cells. When downlink data arrives, the UE is pagedin the whole ERA. The UE uses the ERA Update procedure when it reselectsto a cell belonging to a new ERA. The URA Update used when reselectingto a new URA.

In one or more embodiments, the CU_CNCTD state has some similaritieswith the UTRAN CELL_FACH state with the following differences. Theproposed Cell Update mobility for both ERA_PCH and CU_CNCTD state isadapted to the distributed E-UTRAN architecture. Notably, it iscomplemented with X2 functionality for paging and data forwarding, inorder to avoid frequent S1 path switch. With the CU_CNCTD state,signaling is added to minimize any wastage of resources attempting todeliver data in the source cell if the UE has already imitated itschange to a different cell. It should be noted that the ERA_PCH stateand the CU_CNCTD states as described herein may be independent accessstratum states in some embodiments, and in other embodiments the ERA_PCHstate may be a sub-state of an existing idle ERA_PCH mode and theCU_CNCTD state may be a sub-state of an existing connected CU_CNCTD modein accordance with a 3GPP standard, and the scope of the claimed subjectmatter is not limited in these respects.

In one or more embodiments, mobility handling in the ERA_PCH state isshown in FIG. 1. Network 100 may include a mobility management entity(MME) 116 and a serving gateway (SGW) 118 wherein data transmissions 120to and from UE 110 via eNB1 112 may occur. In network 100, the UE 110initially may be in an HO_CNCTD or CU_CNCTD state and has ongoing uplinkand downlink data transmissions 120 via eNB1 112. The ERA_PCH state maybe entered when eNB1 realizes that the UE 110 has been inactive for along period of time. The decision also may be based on mobility,allowing for fast moving UEs to move around without having to performcell update multiple times. The eNB1 112 becomes the Anchor eNB for thisUE 110 and serves as the S1 termination point. As part of the statechange, a parameter referred to as Anchor ID may be provided to the UE110. This parameter may be used to identify the Anchor eNB such as eNB1112 when UE 110 resurfaces under another eNB such as eNB2 114. The eNB1112 transmits an ERA_PCH command 122 to UE 110. The definition of theE-UTRAN Routing Area (ERA) may be defined either as an ERA identifier(ERA ID), a list of ERA IDs, or as a list of cells. In the case that ERAIDs are used, then it may be assumed that each cell will broadcast viasystem information an ERA ID so that the ERA ID can be known by all UEslocated in the cell. The UE 110 now can move within all cells belongingto the same ERA without having to perform any signaling.

As shown in FIG. 2, if network 100 has downlink data to send to the UE110, the data are forwarded to the Anchor eNB, in this example eNB1 112,and are buffered there in buffer 210. The Anchor eNB, eNB1 112, knowsthat the UE 110 has entered the ERA_PCH state, and thus the location ofUE 110 will be determined. Locating UE 110 may done by sending a pagingmessage 212 on the radio in the cell, eNB1 112, where the UE 110 waslast active. If eNB1 112 does not receive a response, or in parallelwith the previous, eNB1 112 sends an X2 PAGING message 214 to all othereNBs, such as to eNB2 114, controlling cells that belong to the same ERAprovided to the UE 110. It may be assumed that the Anchor eNB, eNB1 112,is able to reach via X2 all eNBs that control cells belonging to thesame ERA.

The UE 110 may perform a Cell Update procedure with eNB2 114 in responseto receiving the X2 paging message 214. The Cell Update message includesthe Anchor ID allowing eNB2 114 to identify the Anchor eNB, eNB1 112. Asa result, eNB2 114 fetches UE context from eNB1 112, and eNB1 112 mayforward the buffered data in buffer 210 to eNB2 114, which in turnforwards the buffered data and the UE context to the UE 110. Note thatat this point network 100 may decide to keep eNB1 112 as the Anchor eNB,for example in order to reduce S1 signaling load, or to re-anchor the S1interface in eNB2 114. In the latter case, a new Anchor ID is providedto UE 110 as part of the Cell Update procedure. At this point, UE 110may be placed by the eNB2 114, or possibly based on implicit rules, inthe CU_CNCTD state or HO_CNCTD state. At a later time, after some periodof inactivity, the UE 110 may again be placed in the ERA_PCH state.

In one more embodiments, eNB2 114 becomes the new Anchor eNB for UE 110after UE 110 has performed a Cell Update procedure to connect with eNB2114. The description, above, was related to downlink data in ERA_PCHstate. If UE 110 has uplink data to transmit while in ERA_PCH state, theUE 110 performs the Cell Update procedure as described, above, with theonly difference being that the Cell Update procedure is not triggered bypaging. Even when there is no uplink or downlink data to transmit, theUE 110 can still perform the Cell Update procedure, for example whenmoving to a cell that does not belong to the current ERA. In this case,the Cell Update procedure may be referred to as an ERA Update procedure,although from a signaling perspective ERA Update may be based on thesame messages as Cell Update. After the ERA Update procedure iscompleted the UE 110 may immediately return to ERA_PCH state. As can beseen from the description so far, the handling of ERA_PCH state may besimilar to the handling of URA_PCH in UMTS. The main difference,however, is that in with the ERA_PCH in accordance with one or moreembodiments, there is no central radio access network (RAN) nodecomparable to a radio network controller (RNC). As a result, in one ormore embodiments the UE 110 is notified of the Anchor ID and signals theAnchor ID as part of the Cell Update procedure. Furthermore, in one ormore embodiments the distributed E-UTRAN architecture discussed hereinalso utilizes the X2 PAGING message as part of the Cell Updateprocedure, although the scope of the claimed subject matter is notlimited in these respects.

Referring now to FIG. 3, a diagram of a network illustrating mobilityhandling in a second access stratum state using buffer request and cellupdate procedures in accordance with one or more embodiments will bediscussed. FIG. 3 shows mobility handling in the CU_CNCTD state.Initially, the UE 110 is in the CU_CNCTD state and may have ongoinguplink and downlink data transmissions via eNB1 112, which is designatedas the Anchor eNB. The UE 110 has an Anchor ID for eNB1 112 which mayhave been provided to the UE 110 for example when the UE 110 was placedin the CU_CNCTD state. The UE 110 then realizes that it is moving awayfrom the cell and sends a Buffer Request message 312 to eNB1 112 inorder to suspend transmission of downlink data. Generally, the BufferRequest message is used for the UE 110 to notify source eNB that the UE110 will change the serving cell using the Cell Update procedure. Thismessage may be defined as radio resource control (RRC) signaling, mediaaccess control (MAC) control element signaling or physical layersignaling.

Next, the UE 110 selects or reselects to a cell controlled by eNB2 114and performs a Cell Update procedure indicating the Anchor ID for the UE110. Based on the Anchor ID, eNB2 114 contacts eNB1 112, and fetches UEcontext in order to resume data transmissions via eNB2 114. As in theERA_PCH case, above, network 100 may decide to keep eNB1 112 as theAnchor eNB, or to perform a path switch procedure in order to re-anchorthe S1 interface on eNB2 114, in which case a new Anchor ID is providedto UE 110 as part of the Cell Update procedure. In the former case, eNB1112 and eNB2 114 will establish a user plane path 314 over the X2interface so that the complete user plane path is S-GW 118, eNB1 112,eNB2 114, and UE 110. Both uplink and downlink data transmissions 120can use this user plane path 314. The benefit of establishing such apath over X2 is to avoid the impact of EPC signaling associated withperforming a path switch at every cell change. The network 100 (orE-UTRAN) may at a later time decide to perform the path switch in orderto re-anchor the S1 interface to eNB2 114, thereby creating a moredirect path from S-GW 118 to eNB2 114 to UE 110. The network 100 (orE-UTRAN) may decide to perform such a path switch based on, for example,the volume of data being transferred. As part of the re-anchoringprocedure, the new Anchor ID may be provided to the UE 110 using an RRCprocedure.

In some embodiments, the UE 110 may move out of the source cell withoutbeing able to send a Buffer Request message 312. One such example is thecase where UE 110 moves out of the source cell while in the sleep periodof Connected DRX (C-DRX) mode. Having awoken from sleep, the UE 110 mayselect or re-select a different cell and may perform a Cell Updateprocedure in the target cell. The target eNB then contacts the sourceeNB and fetches the UE context. If the S1 interface is not re-anchoredto eNB2 114, then the data in eNB1 112 that is not yet successfullydelivered to the source cell may be sent via the newly created X2 path.If the S1 interface is re-anchored to eNB21 114 using a path switch,then any not yet successfully delivered data may be forwarded to eNB2114 using the normal procedures for path switch. As no Buffer Requestwas received by the source eNB, some resources of the source cell mayhave been wasted by the source cell unsuccessfully attempting to deliverdownlink data to the UE 110 while the UE 110 is in the process ofselecting or reselecting to a different cell and performing the CellUpdate procedure in that cell. This procedure, however, still may bebetter than the existing procedure where the UE 110 would have todeclare Radio Link Failure (RLF) and then re-establish the radioresource control (RRC) connection in the new cell.

Thus, in one or more embodiments, as illustrated in the above examples,mobility handling may be as follows. Two new RRC states in the accessstratum are defined: E-UTRAN Routing Area Paging Channel (ERA_PCH) andCell Update Connected (CU_CNCTD). A UE 110 can be in the ERA_PCH stateor the CU_CNCTD state, or a state which is equivalent to the existingbehavior in RRC_CONNECTED mode where handover is used for cell changes.In one or more embodiments, the existing behavior in the RRC_CONNECTEDmay be referred to as Handover Connected (HO_CNCTD). A network orE-UTRAN may choose to implement the ERA_PCH state or the CU_CNCTD stateor both. The HO_CNCTD state also may be available the E-UTRAN as it isthe existing behavior. Both new RRC states correspond to theEMM_Connected state in the Non Access Stratum (NAS) and RRC_CONNECTED inthe Access Stratum (AS). Configuration and/or transition of states maybe done explicitly by the eNB or may be done implicitly based on thepredefined or preconfigured rules. The MME 116 may also play a role inconfiguring the use of the new RRC states.

In one or more embodiments, ERA_PCH is a substrate of the RRC_CONNECTEDstate. Characteristics of the ERA_PCH state are as follows. When inERA_PCH, the UE location is known with the granularity of an ERA,wherein ERA comprises a collection of E-UTRAN cells. UE based mobilityis used wherein the UE 110 performs cell selection and reselection inorder to determine the best cell on which to camp. The UE 110 can movefreely between cells of the same ERA without any signaling with thenetwork. Downlink (DL) and uplink (UL) data transfer with the UE may notbe possible until a Cell Update procedure has been performed. Uponarrival of downlink data, the UE 110 is paged in the whole ERA. The UE110 responds with Cell Update. When selecting or reselecting to a cellbelonging to another ERA, the UE 110 performs an ERA Update procedure.The ERA_PCH state may be considered as similar to URA_PCH in UMTS.

Furthermore, in one or more embodiments, the CU_CNCTD also may beconsidered as a substrate of the RRC_CONNECTED state. When in theCU-CNCTD state, the UE 110 location is known with cell levelgranularity. UE based mobility is used wherein the UE 110 performs cellselection and reselection in order to determine the best cell on whichto camp. The Cell Update procedure may be used to inform the network 100or E-UTRAN whenever the UE 110 changes to a new cell. DL and UL datatransfer with the UE is then possible. Before leaving the source cell inthe CU_CNCTD state, the UE 110 may send a Buffer Request message torequest that the eNB buffers any downlink data that arrives at the eNBfor the UE 110, instead of attempting to deliver the data over the radiointerface. After successful selection or reselection, the UE 110 usesthe Cell Update procedure from the target cell to resume thetransmission of downlink data.

In one or more embodiments, the proposed Cell Update mobility may beapplied to a distributed E-UTRAN architecture, for example an E-UTRANcomprising only eNBs, or to a centralized E-UTRAN architecture byintroducing an eNB gateway (eNB GW) as a centralized node on network100, for example eNB GW 410 as shown in and described with respect toFIG. 4 through FIG. 7, below. In the distributed architecture, there isa notion of an Anchor eNB which is an eNB that terminates the S1interface. The Anchor eNB may be different from the current serving eNBof the UE 110. For a UE 110 in the ERA_PCH state, downlink data may bebuffered at the Anchor eNB, and the UE 110 is paged in the whole ERA byusing an X2 Paging procedure towards all eNBs related to the ERA. For aUE 110 in CU_CNCTD state, when the UE 110 resurfaces under a new cellthat is not controlled by the Anchor eNB, network 100 may decide tore-anchor S1 on the new eNB, or delay re-anchoring in order to minimizeS1 signaling. An Anchor ID may be provided to the UE 110 so that theAnchor ID may be included in the Cell Update procedure message to enablelocating of the Anchor eNB. For a UE 110 in the ERA_PCH state, when theUE 110 resurfaces under a new ERA using the ERA Update procedure, the S1interface typically may be re-anchored immediately.

In one or more embodiments, the ERA_PCH state may be similar to URA_PCHin UMTS. When in ERA_PCH, the UE 110 location is known with thegranularity of an ERA, the ERA being a collection of E-UTRAN cells. TheUE 110 can move freely between cells of the same ERA without anysignaling with network 100. Upon arrival of downlink data, the UE 110 ispaged in the whole ERA. When selecting or reselecting to a cellbelonging to another ERA, the UE 110 performs an ERA Update procedure.It should be noted that the ERA Update procedure may be similar to theCell Update procedure, with an appropriate cause value set to Triggereddue to change of ERA. Furthermore, in one or more embodiments theCU_CNCTD state may be similar to an existing RRC_CONNECTED state in thesense that the UE 110 location is known with cell granularity, and thereis an established RRC connection. In contrast to existing behavior inRRC_CONNECTED, in accordance with one or more embodiments the mobilitymay be UE-driven, that is based on cell selection or reselection, andmay use a Cell Update procedure without using a network-controlledHandover procedure.

The ERA_PCH state and/or the CU_CNCTD state may be entered when network100 determines that this type of mobility is suited for the UE 110. Sucha decision can be made based at least in part on the following factors.The UE 110 subscription may indicate that the ERA_PCH state and/or theCU_CNCTD state is the preferred mobility handling. Network 100 maydetermine that the ERA_PCH state and/or the CU_CNCTD state should beutilized based at least in part on behavior of the UE 110, for exampleif the UE 110 sends sporadic data and/or prefers longer values forConnected mode DRX. Network 100 that the ERA_PCH state and/or theCU_CNCTD state should be utilized based at least in part on the mobilitypattern exhibited by the behavior, for example if the UE 110 is highlymobile. The current state may be configured and/or changed by the eNBfor example by an RRC procedure. Alternatively, transition betweendifferent modes implicitly may be done. For example if there is ongoingdata in the CU_CNCTD state, the UE 110 autonomously may move to theHO_CNCTD state, which means that the UE 110 triggers measurementreporting for the normal handover procedure instead of a Cell Updateprocedure.

Referring now to FIG. 4 and FIG. 5, diagrams of a network illustratingmobility handling in the first access stratum state using a centralizedarchitecture in accordance with one or more embodiments will bediscussed. FIG. 4 and FIG. 5 show the mobility handling for the ERA_PCHstate described herein as applied to a centralized E-UTRAN architectureof network 100. In such an architecture, the eNBs are connected to acentral network node referred to as an eNB gateway (eNB GW) 410. Thehierarchical location of eNB GW 410 may be similar to the Home eNB GW(HeNB GW), an optional functional node in the existing E-UTRANarchitecture, but which, however, implements different functions. The UE110 may receive download data transmissions 120 from SGW 118 via eNB GW410 and eNB1 112. The UE 110 may receive a command 122 to enter into theERA_PCH state. The UE context may be transferred for the ERA_PCH viatransmission 414. As shown in FIG. 5, in one or more embodiments, theeNB GW 410 may be utilized for serving as a long-term anchor for the S1interface towards the EPC, storing of UE context for UEs in the ERA_PCHstate, buffering downlink data in buffer 412 for UEs in the ERA_PCHstate, sending S1 PAGING messages 212 to eNBs controlling cells of theERA, and/or temporary buffering for UEs in the CU_CNCTD state uponreception of a Buffer Request. Context and path switch request 510 maytransfer buffered data and downloaded data transmissions 120 to eNB3310. It should be noted that eNB GW 410 may be used as the mobilityanchor for both the ERA_PCH as shown in FIG. 4 and FIG. 5, and also forthe CU_CNCTD state mobility as shown in and described with respect toFIG. 6 and FIG. 7, below.

Referring now to FIG. 6 and FIG. 7, diagrams of a network illustratingmobility handling in the second access stratum state using a centralizedarchitecture in accordance with one or more embodiments will bediscussed. As shown in FIG. 6 and FIG. 7, if the UE 110 was unable tosend a Buffer Request before leaving the source eNB such as eNB1 112,for example because the UE 110 was in the sleep period of a C-DRX cycle,once the UE 110 performs the Cell Update procedure with the target eNB,such as eNB2 114, any data buffered in the source eNB can be fetchedeither via X2 from eNB1 112, or via S1 from source eNB, eNB1 112 to eNBGW 410 to target eNB, eNB2 114.

Referring now to FIG. 8, a block diagram of an information handlingsystem capable of user equipment controlled mobility in an evolved radioaccess network in accordance with one or more embodiments will bediscussed. Information handling system 800 of FIG. 8 may tangibly embodyany one or more of the network elements described herein, above,including for example the elements of network 100 with greater or fewercomponents depending on the hardware specifications of the particulardevice. In one embodiment, information handling system 800 may tangiblyembody a user equipment (UE) comprising circuitry to enter into anevolved universal mobile telecommunications system (UMTS) terrestrialradio access (E-UTRAN) Routing Area Paging Channel (ERA_PCH) state,wherein the UE is configured with an E-UTRAN Routing Area (ERA)comprising a collection of cell identifiers, and an Anchor identifier(Anchor ID) to identify an anchor evolved Node B (eNB) for the UE,select to a new cell without performing a handover procedure, andperform a cell update procedure in response to the UE selecting to thenew cell, although the scope of the claimed subject matter is notlimited in this respect. In another embodiment, information handlingsystem 800 may tangibly embody a user equipment (UE) comprisingcircuitry to enter into a Cell Update Connected (CU_CNCTD) state,wherein the UE is configured with an Anchor identifier (Anchor ID) toidentify an anchor evolved Node B (eNB) for the UE, select to a newcell, perform a cell update procedure in response to the UE selecting tothe new cell, perform a buffer request procedure in response to the UEselecting to the new cell, and perform a cell update procedure todownload buffered data and to perform data transmission with the newcell, although the scope of the claimed subject matter is not limited inthis respect. Although information handling system 800 represents oneexample of several types of computing platforms, information handlingsystem 800 may include more or fewer elements and/or differentarrangements of elements than shown in FIG. 8, and the scope of theclaimed subject matter is not limited in these respects.

In one or more embodiments, information handling system 800 may includean application processor 810 and a baseband processor 812. Applicationprocessor 810 may be utilized as a general-purpose processor to runapplications and the various subsystems for information handling system800. Application processor 810 may include a single core oralternatively may include multiple processing cores. One or more of thecores may comprise a digital signal processor or digital signalprocessing (DSP) core. Furthermore, application processor 810 mayinclude a graphics processor or coprocessor disposed on the same chip,or alternatively a graphics processor coupled to application processor810 may comprise a separate, discrete graphics chip. Applicationprocessor 810 may include on board memory such as cache memory, andfurther may be coupled to external memory devices such as synchronousdynamic random access memory (SDRAM) 814 for storing and/or executingapplications during operation, and NAND flash 816 for storingapplications and/or data even when information handling system 800 ispowered off. In one or more embodiments, instructions to operate orconfigure the information handling system 800 and/or any of itscomponents or subsystems to operate in a manner as described herein maybe stored on an article of manufacture comprising a non-transitorystorage medium. In one or more embodiments, the storage medium maycomprise any of the memory devices shown in and described herein,although the scope of the claimed subject matter is not limited in thisrespect. Baseband processor 812 may control the broadband radiofunctions for information handling system 800. Baseband processor 812may store code for controlling such broadband radio functions in a NORflash 818. Baseband processor 812 controls a wireless wide area network(WWAN) transceiver 820 which is used for modulating and/or demodulatingbroadband network signals, for example for communicating via a 3GPP LTEor LTE-Advanced network or the like.

In general, WWAN transceiver 820 may operate according to any one ormore of the following radio communication technologies and/or standardsincluding but not limited to: a Global System for Mobile Communications(GSM) radio communication technology, a General Packet Radio Service(GPRS) radio communication technology, an Enhanced Data Rates for GSMEvolution (EDGE) radio communication technology, and/or a ThirdGeneration Partnership Project (3GPP) radio communication technology,for example Universal Mobile Telecommunications System (UMTS), Freedomof Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP LongTerm Evolution Advanced (LTE Advanced), Code division multiple access2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, ThirdGeneration (3G), Circuit Switched Data (CSD), High-SpeedCircuit-Switched Data (HSCSD), Universal Mobile TelecommunicationsSystem (Third Generation) (UMTS (3G)), Wideband Code Division MultipleAccess (Universal Mobile Telecommunications System) (W-CDMA (UMTS)),High Speed Packet Access (HSPA), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed PacketAccess Plus (HSPA+), Universal Mobile TelecommunicationsSystem-Time-Division Duplex (UMTS-TDD), Time Division-Code DivisionMultiple Access (TD-CDMA), Time Division-Synchronous Code DivisionMultiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8(Pre-4th Generation) (3GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd GenerationPartnership Project Release 9), 3GPP Rel. 10 (3rd Generation PartnershipProject Release 10), 3GPP Rel. 11 (3rd Generation Partnership ProjectRelease 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 12), 3GPPRel. 14 (3rd Generation Partnership Project Release 12), 3GPP LTE Extra,LTE Licensed-Assisted Access (LAA), UMTS Terrestrial Radio Access(UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long TermEvolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G),Code division multiple access 2000 (Third generation) (CDMA2000 (3G)),Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total Access CommunicationSystem/Extended Total Access Communication System (TACS/ETACS), DigitalAMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), MobileTelephone System (MTS), Improved Mobile Telephone System (IMTS),Advanced Mobile Telephone System (AMTS), OLT (Norwegian for OffentligLandmobil Telefoni, Public Land Mobile Telephony), MTD (Swedishabbreviation for Mobiltelefonisystem D, or Mobile telephony system D),Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UMA), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth®, Wireless GigabitAlliance (WiGig) standard, millimeter wave (mmWave) standards in generalfor wireless systems operating at 10-90 GHz and above such as WiGig,IEEE 802.11ad, IEEE 802.11ay, and so on, and/or general telemetrytransceivers, and in general any type of RF circuit or RFI sensitivecircuit. It should be noted that such standards may evolve over time,and/or new standards may be promulgated, and the scope of the claimedsubject matter is not limited in this respect.

The WWAN transceiver 820 couples to one or more power amps 842respectively coupled to one or more antennas 824 for sending andreceiving radio-frequency signals via the WWAN broadband network. Thebaseband processor 812 also may control a wireless local area network(WLAN) transceiver 826 coupled to one or more suitable antennas 828 andwhich may be capable of communicating via a Wi-Fi, Bluetooth®, and/or anamplitude modulation (AM) or frequency modulation (FM) radio standardincluding an IEEE 802.11 a/b/g/n standard or the like. It should benoted that these are merely example implementations for applicationprocessor 810 and baseband processor 812, and the scope of the claimedsubject matter is not limited in these respects. For example, any one ormore of SDRAM 614, NAND flash 816 and/or NOR flash 818 may compriseother types of memory technology such as magnetic memory, chalcogenidememory, phase change memory, or ovonic memory, and the scope of theclaimed subject matter is not limited in this respect.

In one or more embodiments, application processor 810 may drive adisplay 630 for displaying various information or data, and may furtherreceive touch input from a user via a touch screen 832 for example via afinger or a stylus. An ambient light sensor 834 may be utilized todetect an amount of ambient light in which information handling system800 is operating, for example to control a brightness or contrast valuefor display 830 as a function of the intensity of ambient light detectedby ambient light sensor 834. One or more cameras 836 may be utilized tocapture images that are processed by application processor 810 and/or atleast temporarily stored in NAND flash 816. Furthermore, applicationprocessor may couple to a gyroscope 838, accelerometer 840, magnetometer842, audio coder/decoder (CODEC) 844, and/or global positioning system(GPS) controller 846 coupled to an appropriate GPS antenna 848, fordetection of various environmental properties including location,movement, and/or orientation of information handling system 800.Alternatively, controller 846 may comprise a Global Navigation SatelliteSystem (GNSS) controller. Audio CODEC 844 may be coupled to one or moreaudio ports 850 to provide microphone input and speaker outputs eithervia internal devices and/or via external devices coupled to informationhandling system via the audio ports 850, for example via a headphone andmicrophone jack. In addition, application processor 810 may couple toone or more input/output (I/O) transceivers 852 to couple to one or moreI/O ports 854 such as a universal serial bus (USB) port, ahigh-definition multimedia interface (HDMI) port, a serial port, and soon. Furthermore, one or more of the I/O transceivers 852 may couple toone or more memory slots 856 for optional removable memory such assecure digital (SD) card or a subscriber identity module (SIM) card,although the scope of the claimed subject matter is not limited in theserespects.

Referring now to FIG. 9, an isometric view of an information handlingsystem of FIG. 8 that optionally may include a touch screen inaccordance with one or more embodiments will be discussed. FIG. 9 showsan example implementation of information handling system 800 of FIG. 8tangibly embodied as a cellular telephone, smartphone, or tablet typedevice or the like. The information handling system 800 may comprise ahousing 910 having a display 830 which may include a touch screen 832for receiving tactile input control and commands via a finger 916 of auser and/or a via stylus 918 to control one or more applicationprocessors 810. The housing 910 may house one or more components ofinformation handling system 800, for example one or more applicationprocessors 810, one or more of SDRAM 814, NAND flash 816, NOR flash 818,baseband processor 812, and/or WWAN transceiver 820. The informationhandling system 800 further may optionally include a physical actuatorarea 920 which may comprise a keyboard or buttons for controllinginformation handling system via one or more buttons or switches. Theinformation handling system 800 may also include a memory port or slot856 for receiving non-volatile memory such as flash memory, for examplein the form of a secure digital (SD) card or a subscriber identitymodule (SIM) card. Optionally, the information handling system 800 mayfurther include one or more speakers and/or microphones 924 and aconnection port 854 for connecting the information handling system 800to another electronic device, dock, display, battery charger, and so on.In addition, information handling system 800 may include a headphone orspeaker jack 928 and one or more cameras 836 on one or more sides of thehousing 910. It should be noted that the information handling system 800of FIG. 9 may include more or fewer elements than shown, in variousarrangements, and the scope of the claimed subject matter is not limitedin this respect.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

Referring now to FIG. 10, example components of a wireless device suchas User Equipment (UE) device 110 in accordance with one or moreembodiments will be discussed. User equipment (UE) may correspond, forexample, to UE 110 of network 100, although the scope of the claimedsubject matter is not limited in this respect. In some embodiments, UEdevice 1000 may include application circuitry 1002, baseband circuitry1004, Radio Frequency (RF) circuitry 1006, front-end module (FEM)circuitry 1008 and one or more antennas 1010, coupled together at leastas shown.

Application circuitry 1002 may include one or more applicationprocessors. For example, application circuitry 1002 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The one or more processors may include anycombination of general-purpose processors and dedicated processors, forexample graphics processors, application processors, and so on. Theprocessors may be coupled with and/or may include memory and/or storageand may be configured to execute instructions stored in the memoryand/or storage to enable various applications and/or operating systemsto run on the system.

Baseband circuitry 1004 may include circuitry such as, but not limitedto, one or more single-core or multi-core processors. Baseband circuitry1004 may include one or more baseband processors and/or control logic toprocess baseband signals received from a receive signal path of RFcircuitry 1006 and to generate baseband signals for a transmit signalpath of the RF circuitry 1006. Baseband processing circuitry 1004 mayinterface with the application circuitry 1002 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 1006. For example, in some embodiments, the basebandcircuitry 804 may include a second generation (2G) baseband processor1004 a, third generation (3G) baseband processor 1004 b, fourthgeneration (4G) baseband processor 1004 c, and/or one or more otherbaseband processors 1004 d for other existing generations, generationsin development or to be developed in the future, for example fifthgeneration (5G), sixth generation (6G), and so on. Baseband circuitry1004, for example one or more of baseband processors 1004 a through 1004d, may handle various radio control functions that enable communicationwith one or more radio networks via RF circuitry 1006. The radio controlfunctions may include, but are not limited to, signal modulation and/ordemodulation, encoding and/or decoding, radio frequency shifting, and soon. In some embodiments, modulation and/or demodulation circuitry ofbaseband circuitry 1004 may include Fast-Fourier Transform (FFT),precoding, and/or constellation mapping and/or demapping functionality.In some embodiments, encoding and/or decoding circuitry of basebandcircuitry 804 may include convolution, tail-biting convolution, turbo,Viterbi, and/or Low Density Parity Check (LDPC) encoder and/or decoderfunctionality. Embodiments of modulation and/or demodulation and encoderand/or decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, baseband circuitry 1004 may include elements of aprotocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. Processor 1004 e of the baseband circuitry 1004may be configured to run elements of the protocol stack for signaling ofthe PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, thebaseband circuitry may include one or more audio digital signalprocessors (DSP) 1004 f The one or more audio DSPs 1004 f may includeelements for compression and/or decompression and/or echo cancellationand may include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of baseband circuitry 1004 and application circuitry 1002 maybe implemented together such as, for example, on a system on a chip(SOC).

In some embodiments, baseband circuitry 1004 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, baseband circuitry 1004 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which baseband circuitry 804 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 1006 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, RF circuitry 1006 may include switches, filters,amplifiers, and so on, to facilitate the communication with the wirelessnetwork. RF circuitry 1006 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from FEM circuitry1008 and provide baseband signals to baseband circuitry 1004. RFcircuitry 1006 may also include a transmit signal path which may includecircuitry to up-convert baseband signals provided by the basebandcircuitry 1004 and provide RF output signals to FEM circuitry 1008 fortransmission.

In some embodiments, RF circuitry 1006 may include a receive signal pathand a transmit signal path. The receive signal path of RF circuitry 1006may include mixer circuitry 1006 a, amplifier circuitry 1006 b andfilter circuitry 1006 c. The transmit signal path of RF circuitry 1006may include filter circuitry 1006 c and mixer circuitry 1006 a. RFcircuitry 1006 may also include synthesizer circuitry 1006 d forsynthesizing a frequency for use by the mixer circuitry 1006 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 1006 a of the receive signal path may be configuredto down-convert RF signals received from FEM circuitry 1008 based on thesynthesized frequency provided by synthesizer circuitry 1006 d.Amplifier circuitry 1006 b may be configured to amplify thedown-converted signals and the filter circuitry 1006 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to baseband circuitry1004 for further processing. In some embodiments, the output basebandsignals may be zero-frequency baseband signals, although this is not arequirement. In some embodiments, mixer circuitry 1006 a of the receivesignal path may comprise passive mixers, although the scope of theembodiments is not limited in this respect.

In some embodiments, mixer circuitry 1006 a of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by synthesizer circuitry 1006 d togenerate RF output signals for FEM circuitry 1008. The baseband signalsmay be provided by the baseband circuitry 1004 and may be filtered byfilter circuitry 1006 c. Filter circuitry 1006 c may include a low-passfilter (LPF), although the scope of the embodiments is not limited inthis respect.

In some embodiments, mixer circuitry 1006 a of the receive signal pathand the mixer circuitry 1006 a of the transmit signal path may includetwo or more mixers and may be arranged for quadrature down conversionand/or up conversion respectively. In some embodiments, mixer circuitry1006 a of the receive signal path and the mixer circuitry 1006 a of thetransmit signal path may include two or more mixers and may be arrangedfor image rejection, for example Hartley image rejection. In someembodiments, mixer circuitry 806 a of the receive signal path and themixer circuitry 1006 a may be arranged for direct down conversion and/ordirect up conversion, respectively. In some embodiments, mixer circuitry1006 a of the receive signal path and mixer circuitry 1006 a of thetransmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, RFcircuitry 1006 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry, and baseband circuitry 804may include a digital baseband interface to communicate with RFcircuitry 1006. In some dual-mode embodiments, separate radio integratedcircuit (IC) circuitry may be provided for processing signals for one ormore spectra, although the scope of the embodiments is not limited inthis respect.

In some embodiments, synthesizer circuitry 1006 d may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 1006 dmay be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

Synthesizer circuitry 1006 d may be configured to synthesize an outputfrequency for use by mixer circuitry 1006 a of RF circuitry 1006 basedon a frequency input and a divider control input. In some embodiments,synthesizer circuitry 1006 d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either baseband circuitry 1004 orapplications processor 1002 depending on the desired output frequency.In some embodiments, a divider control input (e.g., N) may be determinedfrom a look-up table based on a channel indicated by applicationsprocessor 1002.

Synthesizer circuitry 1006 d of RF circuitry 1006 may include a divider,a delay-locked loop (DLL), a multiplexer and a phase accumulator. Insome embodiments, the divider may be a dual modulus divider (DMD) andthe phase accumulator may be a digital phase accumulator (DPA). In someembodiments, the DMD may be configured to divide the input signal byeither N or N+1, for example based on a carry out, to provide afractional division ratio. In some example embodiments, the DLL mayinclude a set of cascaded, tunable, delay elements, a phase detector, acharge pump and a D-type flip-flop. In these embodiments, the delayelements may be configured to break a VCO period up into Nd equalpackets of phase, where Nd is the number of delay elements in the delayline. In this way, the DLL provides negative feedback to help ensurethat the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1006 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency, for example twice the carrier frequency, four times thecarrier frequency, and so on, and used in conjunction with quadraturegenerator and divider circuitry to generate multiple signals at thecarrier frequency with multiple different phases with respect to eachother. In some embodiments, the output frequency may be a localoscillator (LO) frequency (fLO). In some embodiments, RF circuitry 1006may include an in-phase and quadrature (IQ) and/or polar converter.

FEM circuitry 1008 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 1010, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 1006 for furtherprocessing. FEM circuitry 1008 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by RF circuitry 1006 for transmission by one ormore of the one or more antennas 1010.

In some embodiments, FEM circuitry 1008 may include a transmit/receive(TX/RX) switch to switch between transmit mode and receive modeoperation. FEM circuitry 1008 may include a receive signal path and atransmit signal path. The receive signal path of FEM circuitry 1008 mayinclude a low-noise amplifier (LNA) to amplify received RF signals andto provide the amplified received RF signals as an output, for exampleto RF circuitry 1006. The transmit signal path of FEM circuitry 1008 mayinclude a power amplifier (PA) to amplify input RF signals, for exampleprovided by RF circuitry 1006, and one or more filters to generate RFsignals for subsequent transmission, for example by one or more ofantennas 1010. In some embodiments, UE device 1000 may includeadditional elements such as, for example, memory and/or storage,display, camera, sensor, and/or input/output (I/O) interface, althoughthe scope of the claimed subject matter is not limited in this respect.

The following are example implementations of the subject matterdescribed herein. It should be noted that any of the examples and thevariations thereof described herein may be used in any permutation orcombination of any other one or more examples or variations, althoughthe scope of the claimed subject matter is not limited in theserespects. In example one, an apparatus of a user equipment (UE) maycomprise circuitry to enter into an evolved universal mobiletelecommunications system (UMTS) terrestrial radio access (E-UTRAN)Routing Area Paging Channel (ERA_PCH) state, wherein the UE isconfigured with an E-UTRAN Routing Area (ERA) comprising a collection ofcell identifiers, and an Anchor identifier (Anchor ID) to identify ananchor evolved Node B (eNB) for the UE, reselect to a new cell withoutperforming a handover procedure, and perform a cell update procedure. Inexample two, the subject matter of example one or any of the examplesdescribed herein further may include circuitry to perform the cellupdate procedure with a cause value indicating an ERA change if the UEreselects to a cell that is not part of the ERA. In example three, thesubject matter of example one or any of the examples described hereinfurther may include circuitry to perform the cell update procedure inresponse to a paging signal. In example four, the subject matter ofexample one or any of the examples described herein further may includecircuitry to perform the cell update procedure if the UE as uplink datafor transmission. In example five, the Anchor ID may identify an eNB oran eNB gateway (eNB GW) to buffer data or store a UE context during cellselection. In example six, the subject matter of example one or any ofthe examples described herein further may comprise the UE to indicatethe Anchor ID during the cell update procedure. In example seven, thesubject matter of example one or any of the examples described hereinfurther may include circuitry to receive a new Anchor ID during the cellupdate procedure if the Anchor ID is changed. In example eight, thesubject matter of example one or any of the examples described hereinfurther may include circuitry to receive new ERA information comprisinga collection of cell identifiers during the cell update procedure if thecell update procedure is triggered by an ERA change. In example nine,the subject matter of example one or any of the examples describedherein further may include circuitry to change to a Cell UpdateConnected (CU_CNCTD) during the update procedure. In example ten, thesubject matter of example one or any of the examples described hereinfurther may comprise the ERA to be broadcast by an eNB as an ERAidentifier (ERA ID) to the UE as system information.

In example eleven, an apparatus of a user equipment (UE) may comprisecircuitry to enter into a Cell Update Connected (CU_CNCTD) state,wherein the UE is configured with an Anchor identifier (Anchor ID) toidentify an anchor evolved Node B (eNB) for the UE, reselect to a newcell, perform a cell update procedure, perform a buffer requestprocedure in response to the UE reselecting to the new cell, and performa cell update procedure to download buffered data and to perform datatransmission with the new cell. In example twelve, the subject matter ofexample eleven or any of the examples described herein further maycomprise the Anchor ID to identify an eNB or an eNB gateway (eNB GW) tobuffer data or store a UE context during cell reselection. In examplethirteen, the subject matter of example eleven or any of the examplesdescribed herein further may comprise the UE to indicate the Anchor IDduring the cell update procedure. In example fourteen, the subjectmatter of example eleven or any of the examples described herein furthermay include circuitry to receive a new Anchor ID during the cell updateprocedure if the Anchor ID is changed as part of the cell updateprocedure or another radio resource control (RRC) procedure.

In example fifteen, one or more computer-readable media may haveinstructions stored thereon that, if executed by user equipment (UE),result in entering into an evolved universal mobile telecommunicationssystem (UMTS) terrestrial radio access (E-UTRAN) Routing Area PagingChannel (ERA_PCH) state, wherein the UE is configured with an E-UTRANRouting Area (ERA) comprising a collection of cell identifiers, and anAnchor identifier (Anchor ID) to identify an anchor an evolved Node B(eNB) for the UE, reselecting to a new cell without performing ahandover procedure, and performing a cell update procedure in responseto the UE reselecting to the new cell, in response to the UE receiving apaging signal, or if the UE has uplink data for transmission. In examplesixteen, the subject matter of example fifteen or any of the examplesdescribed herein further may include instructions, if executed, toresult in performing the cell update procedure with a cause valueindicating an ERA change if the UE reselects to a cell that is not partof the ERA. In example seventeen, the subject matter of example fifteenor any of the examples described herein further may includeinstructions, if executed, to result in the Anchor ID identifying an eNBor an eNB gateway (eNB GW) to buffer data or store a UE context duringcell reselection. In example eighteen, the subject matter of examplefifteen or any of the examples described herein further may includeinstructions, if executed, to result in the UE indicating the Anchor IDduring the cell update procedure. In example nineteen, the subjectmatter of example fifteen or any of the examples described hereinfurther may include instructions, if executed, to result in receiving anew Anchor ID during the cell update procedure if the Anchor ID ischanged. In example twenty, the subject matter of example fifteen or anyof the examples described herein further may include instructions, ifexecuted, to result in receiving new ERA information comprising acollection of cell identifiers during the cell update procedure if thecell update procedure is triggered by an ERA change. In exampletwenty-one, the subject matter of example fifteen or any of the examplesdescribed herein further may include instructions, if executed, toresult in the ERA being broadcast by an eNB as an ERA identifier (ERAID) to the UE as system information.

In example twenty-two, one or more computer-readable media may haveinstructions stored thereon that, if executed by user equipment (UE),result in entering into a Cell Update Connected (CU_CNCTD) state,wherein the UE is configured with an Anchor identifier (Anchor ID) toidentify an anchor evolved Node B (eNB) for the UE, reselecting to a newcell, performing a cell update, performing a buffer request procedure inresponse to the UE reselecting to the new cell, and performing a cellupdate procedure to download buffered data and to perform datatransmission with the new cell. In example twenty-three, the subjectmatter of example twenty-two or any of the examples described hereinfurther may include instructions, if executed, to result in the AnchorID identifying an eNB or an eNB gateway (eNB GW) to buffer data or storea UE context during cell reselection. In example twenty-four, thesubject matter of example twenty-two or any of the examples describedherein further may include instructions, if executed, to result in theUE indicating the Anchor ID during the cell update procedure. In exampletwenty-five, the subject matter of example twenty-two or any of theexamples described herein further may include instructions, if executed,to result in receiving a new Anchor ID during the cell update procedureif the Anchor ID is changed as part of the cell update procedure oranother radio resource control (RRC) procedure.

Although the claimed subject matter has been described with a certaindegree of particularity, it should be recognized that elements thereofmay be altered by persons skilled in the art without departing from thespirit and/or scope of claimed subject matter. It is believed that thesubject matter user equipment controlled mobility in an evolved radioaccess network and many of its attendant utilities will be understood bythe forgoing description, and it will be apparent that various changesmay be made in the form, construction and/or arrangement of thecomponents thereof without departing from the scope and/or spirit of theclaimed subject matter or without sacrificing all of its materialadvantages, the form herein before described being merely an explanatoryembodiment thereof, and/or further without providing substantial changethereto. It is the intention of the claims to encompass and/or includesuch changes.

What is claimed is:
 1. User equipment (UE) comprising processingcircuitry to: enter into a Cell Update Connected (CU_CNCTD) state,wherein the UE is configured with an Anchor identifier (Anchor ID) toidentify an anchor evolved Node B (eNB) for the UE; reselect to a newcell; perform a cell update procedure in response to the UE reselectingto the new cell; performing a buffer request procedure in the currentcell prior to the UE reselecting to the new cell; and perform a cellupdate procedure in the new cell to resume transmission of buffered datavia the new cell.
 2. The UE as claimed in claim 1, wherein the Anchor IDidentifies an eNB or an eNB gateway (eNB GW) to buffer data or store aUE context during cell reselection.
 3. The UE as claimed in claim 1,wherein the UE indicates the Anchor ID during the cell update procedure.4. The UE as claimed in claim 1, comprising processing circuitry toreceive a new Anchor ID during the cell update procedure if the AnchorID is changed as part of the cell update procedure or another radioresource control (RRC) procedure.
 5. An article of manufacturecomprising a non-transitory medium having instructions stored thereonthat, if executed by user equipment (UE), result in: entering into aCell Update Connected (CU_CNCTD) state, wherein the UE is configuredwith an Anchor identifier (Anchor ID) to identify an anchor evolved NodeB (eNB) for the UE; reselecting to a new cell; performing a cell updateprocedure in response to the UE reselecting to the new cell; performinga buffer request procedure in the current cell prior to the UEreselecting to a new cell; and performing a cell update procedure in thenew cell to resume transmission of buffered data via the new cell. 6.The article of manufacture as claimed in claim 5, wherein the Anchor IDidentifies an eNB or an eNB gateway (eNB GW) to buffer data or store aUE context during cell reselection.
 7. The article of manufacture asclaimed in claim 5, wherein the UE indicates the Anchor ID during thecell update procedure.
 8. The article of manufacture as claimed in claim5, wherein the instructions, if executed, result in receiving a newAnchor ID during the cell update procedure if the Anchor ID is changedas part of the cell update procedure or another radio resource control(RRC) procedure.